As soon as a need for release is initiated, the Release Manager must co-ordinate with the Change Coordinator and gather detailed information about the release. The type of release and deployment should be understood, and the release must be classified (based on the defined rules).

Few examples of Release Classifications may include:

• Minor Release – This class of release would typically consist of small enhancements and fixes, some of which may already have been issued as emergency fixes. A minor upgrade or release usually supersedes all preceding emergency fixes.
• Major Release – This class of release typically consists of large areas of new functionality and could eliminate temporary fixes or problems. A major upgrade or release that supersedes all preceding minor or emergency releases, upgrades or fixes.
• Emergency Release – This class of release typically contains fixes to a small number of problems / known errors or enhancements needed to meet a business or service priority.
  Based on the Release Classification, the Release Manager must identify and assign the Release Policy, which the release must follow. The Release Policy details all attributes of a release that need to be in place.

The Release Policy would contain the definition and unique schema for identification, identified deployment model, numbering and naming conventions of various types of releases, the expected frequency and use of various release types, the various deployment options, authority for acceptance, the integration with the Change Management and Configuration Management activities to ensure the integrity of the baseline, back out / remediation plan etc. Release units must be defined specific to the implementation. The Release Manager must also analyse if there are any dependencies of the release with any other releases